Vehicle event recorders with integrated web server

ABSTRACT

Vehicle event recorders are arranged with integrated web servers to provide a simple user interface and control mechanism which may be address with commonly available hardware and software. A vehicle event recorder of these inventions couples to a network having a workstation node. The workstation having either of the many available web browsers can be used to view, address, control, perform data transfer, et cetera, by way of data exchange in accordance with simple IP protocols. A vehicle equipped with these systems returns to a household to make a network connection. A local server is used to see all exposed system controls as provided by predefined web pages provided by a web server integrated as part of the vehicle event recorder unit.

BACKGROUND OF THE INVENTIONS

1. Field

The following inventions disclosure is generally concerned with vehicle event recorder systems and specifically concerned with vehicle event recorder systems having integrated web server modules.

2. Prior Art

The inventions presented in U.S. Pat. No. 6,947,817 by inventor Diem for nonintrusive diagnostic tools for testing oxygen sensor operation relates to a diagnostic system for testing a vehicle where such systems include a wireless communications link between a vehicle any remote network of server computers. In particular, a WiFi type access points allowed an analyzer to communicate by way the Internet with a server computer hosting and oxygen sensor SOAP (simple object access protocol) service. In a nutshell, the system relates to smog sensors for automobiles which communicate with remote servers by way of a WiFi communications links.

Video surveillance systems are used to provide video records of events, incidents, happenings, et cetera in locations of special interest. For example, retail banking offices are generally protected with video surveillance systems which provide video evidence in case of robbery. While video surveillance systems are generally used in fixed location scenarios, mobile video surveillance systems are also commonly used today.

In particular, video systems have been configured for use in conjunction with an automobile and especially for use with police cruiser type automobiles. As a police cruiser is frequently quite near the scene of an active crime, important image information may be captured by video cameras installed on the police cruiser. Specific activity of interest which may occur about an automobile is not always associated with crime and criminals. Sometimes events which occur in the environments immediately about an automobile are of interest for reasons having nothing to do with crime. In example, a simple traffic accident where two cars come together in a collision may be the subject of video evidence of value. Events and circumstances leading up to the collision accident may be preserved such that an accurate reconstruction can be created. This information is useful when trying come to a determination as to cause, fault and liability. As such, general use of video systems in conjunction with automobiles is quickly becoming an important tool useful for the protection of all. Some examples of the systems are illustrated below with reference to pertinent documents.

Inventor Schmidt presents in U.S. Pat. No. 5,570,127, a video recording system for a passenger vehicle, namely a school bus, which has two video cameras one for an inside bus view and one for a traffic view, a single recorder, and a system whereby the two cameras are multiplexed at appropriate times, to the recording device. A switching signal determines which of the two video cameras is in communication with the video recorder so as to view passengers on the passenger vehicle at certain times and passing traffic at other times.

Thomas Doyle of San Diego, Calif. and QUALCOMM Inc. also of San Diego, present an invention for a method and apparatus for detecting fault conditions in a vehicle data recording device to detect tampering or unauthorized access, in U.S. Pat. No. 5,586,130. The system includes vehicle sensors for monitoring one or more operational parameters of the vehicle. The fault detection technique contemplates storing a current time value at regular intervals during periods in which the recording device is provided with a source of main power. Inventor Doyle also teaches in the U.S. Pat. No. 5,815,071, a method and apparatus for monitoring parameters of vehicle electronic control units.

A “computerized vehicle log” is presented by Dan Kikinis of Saratoga Calif. in U.S. Pat. No. 5,815,093. The vehicle accident recording system employs a digital camera connected to a controller in nonvolatile memory, and an accident sensing interrupter. The oldest memory is overwritten by the newest images, until an accident is detected at which time the memory is blocked from further overwrites to protect the more vital images, which may include important information about the accident. Mr. Kikinis instructs that in preferred embodiments, the system has a communications port whereby stored images are downloaded after an accident to a digital device capable of displaying images. This feature is described in greater detail in the specification which indicates a wired download to a server having specialized image handling and processing software thereon.

Inventor Mr. Turner of Compton, Calif., no less, teaches an antitheft device for an automotive vehicle having both an audible alarm and visual monitor system. Video monitor operators are responsible for monitoring and handling an emergency situation and informing a 911 emergency station. This system is presented in U.S. Pat. No. 6,002,326.

A vehicle accident video recorder, in particular, a railroad vehicle accident video recorder, is taught by inventors Cox et al. In this system, a method and monitoring unit for recording the status of the railroad vehicle prior to a potential accident is presented. The monitoring unit continuously monitors the status of an emergency brake of the railroad vehicle and the status of a horn of the railroad vehicle. Video images are recorded and captured for a predetermined period of time after detecting that the emergency brake or horn blast has been applied as an event trigger. This invention is the subject of U.S. Pat. No. 6,088,635.

A vehicle crash data recorder is presented by inventor Ferguson of Bellaire, Ohio in U.S. Pat. No. 6,185,490. The apparatus is arranged with a three stage memory to record and retain information. And further it is equipped with a series and parallel connectors to provide instant on-scene access to accident data. It is important to note that Ferguson finds it important to include the possibility of on-site access to the data. Further, that Ferguson teaches use of a wired connection in the form of a serial or parallel hardwire connector. This teaching of Ferguson is common in many advanced systems configured as vehicle event recorders.

A traffic accident data recorder and traffic accident reproduction system and method is presented as U.S. Pat. No. 6,246,933. A plurality of sensors for registering vehicle operation parameters including at least one vehicle mounted digital video, audio camera is included for sensing storing and updating operational parameters. A rewritable, nonvolatile memory is provided for storing those processed operational parameters and video images and audio signals, which are provided by the microprocessor controller. Data is converted to a computer readable form and read by a computer such that an accident can be reconstructed via data collected.

U.S. Pat. No. 6,298,290 presented by Abe et al, teaches a memory apparatus for vehicle information data. A plurality of sensors including a CCD camera collision center of vehicle speed sensors, steering angle sensor, brake pressure sensor, acceleration sensor, are all coupled to a control unit. Further, the control unit passes information to a flash memory and a RAM memory subject to an encoder. The information collected is passed through a video output terminal. This illustrates another hardwire system and the importance placed by experts in the art on a computer hardware interface. This is partly due to the fact that video systems are typically data intensive and wired systems are necessary as they have bandwidth sufficient for transfers of large amounts of data.

Mazzilli of Bayside, N.Y. teaches in U.S. Pat. No. 6,333,759 a 360° automobile video camera system. A complex mechanical mount provides for a single camera to adjust its viewing angle giving a 360° range for video recording inside and outside of an automotive vehicle.

U.S. Pat. No. 6,389,339 granted to Inventor Just, of Alpharetta, Ga. teaches a vehicle operation monitoring system and method. Operation of a vehicle is monitored with an onboard video camera linked with a radio transceiver. A monitoring service includes a cellular telecommunications network to view a video data received from the transceiver to a home-base computer. These systems are aimed at parental monitoring of adolescent driving. The mobile modem is designed for transmitting live video information into the network as the vehicle travels.

Morgan, Hausman, Chilek, Hubenak, Kappler, Witz, and Wright with their heads together invented an advanced law enforcement and response technology in U.S. Pat. No. 6,411,874 granted Jun. 25, 2002. A central control system affords intuitive and easy control of numerous subsystems associated with a police car or other emergency vehicle. This highly integrated system provides advanced control apparatus which drives a plurality of detector systems including video and audio systems distributed about the vehicle. A primary feature included in this device includes an advanced user interface and display system, which permits high level driver interaction with the system.

Inventor Lambert teaches in U.S. Pat. No. 6,421,080 a “digital surveillance system with pre-event recording”. Pre-event recording is important in accident recording systems, because detection of the accident generally happens after the accident has occurred. A first memory is used for temporary storage. Images are stored in the temporary storage continuously until a trigger is activated which indicates an accident has occurred at which time images are transferred to a more permanent memory.

Systems taught by Gary Rayner in U.S. Pat. Nos. 6,389,340; 6,405,112; 6,449,540; and 6,718,239, each directed to cameras for automobiles which capture video images, both of forward-looking and driver views, and store recorded images locally on a mass storage system. An operator, at the end of the vehicle service day, puts a wired connector into a device port and downloads information into a desktop computer system having specialized application software whereby the images and other information can be played-back and analyzed at a highly integrated user display interface.

It is not possible in the systems Rayner teaches for an administrative operator to manipulate or otherwise handle the data captured in the vehicle at an off-site location without human intervention. It is necessary for a download operator to transfer data captured from the recorder unit device to a disconnected computer system. While proprietary ‘DriveCam’ files can be e-mailed or otherwise transferred through the Internet, those files are in a format with a can only be digested by desktop software running at a remote computer. It is necessary to have the DriveCam desktop application on the remote computer. In order that the files be properly read. In this way, data captured by the vehicles is totally unavailable to some parties having an interest in the data. Namely those parties who do not have access to a computer appropriately arranged with the specific DriveCam application software. A second and major disadvantage is systems presented by Rayner includes necessity that a human operator service the equipment each day in a manual download action.

Remote reporting and manipulation of automobile systems is not entirely new. The following are very important teachings relating to some automobile systems having a wireless communications link component.

Inventors Fan et al, teach inventions of methods and systems for detecting vehicle collision using global positioning system GPS. The disclosure of Jun. 12, 2001 resulted in granted patent having U.S. Pat. No. 6,459,988. A GPS receiver is combined with wireless technology to automatically report accident and third parties remotely located. A system uses the GPS signals to determine when an acceleration value exceeds the preset threshold which is meant to be indicative of an accident having occurred.

Of particular interest include inventions presented by inventors Nagda et al., in the document numbered U.S. Pat. No. 6,862,524 entitled using location data to determine trafficking route information. In this system for determining and disseminating traffic information or route information, traffic condition information is collected from mobile units that provide their location or position information. Further route information may be utilized to determine whether a mobile unit is allowed or prohibited from traveling along a certain route.

A common assignee, (Road Inc., owns the preceding two patents in addition to the following: U.S. Pat. Nos. 6,529,159; 6,552,682; 6,594,576; 6,664,922; 6,795,017; 6,832,140; 6,867,733; 6,882,313; and 6,922,566. As such, @Road Inc., must be considered a major innovator in position technologies arts as they relate to mobile vehicles and remote server computers.

General Motors Corp. teaches in U.S. Pat. No. 6,728,612, an automated telematics test system and method. The invention provides a method and system testing a telematics system in a mobile vehicle a test command from a test center to a call center is based on a test script. The mobile vehicle is continuously in contact by way of cellular communication networks with a remotely located host computer.

Inventor Earl Diem and Delphi Technologies Inc., had granted to them on Sep. 20, 2005, U.S. Pat. No. 6,947,817. The nonintrusive diagnostic tool for sensing oxygen sensor operation include a scheme or an oxygen analyzer deployed in a mobile vehicle communicates by way of an access point to a remotely located server. A diagnostic heuristic is used to analyze the data and confirm proper operation of the sensor. Analysis may be performed by a mainframe computer quickly note from the actual oxygen sensor.

Similar patents including special relationships between mobile vehicles and remote host computers include those presented by various inventors in U.S. Pat. Nos. 6,735,503; 6,739,078; 6,760,757; 6,810,362; 6,832,141; and 6,850,823.

Another special group of inventions owned by Reynolds and Reynolds Holding Inc., is taught first by Lightner et al, in U.S. Pat. No. 6,928,348 issued Aug. 9, 2005. In these inventions, Internet based emission tests are performed on vehicles having special wireless couplings to computer networks. Data may be further transferred to entities of particular interest including the EPA or California Air Resources Board, for example, or particular insurance companies and other organizations concerned with vehicle emissions and environment.

Other patents held by Reynolds and Reynolds Holding Inc., include those relating to reporting of automobile performance parameters to remote servers via wireless links. Specifically, an onboard data bus OBD system is coupled to a microprocessor, by way of a standard electrical connector. The microprocessor periodically receives data and transmits it into the wireless communications system. This information is more fully described in U.S. patent granted Oct. 21, 2003 numbered U.S. Pat. No. 6,636,790. Inventors Lightner et al, present method and apparatus for remotely characterizing the vehicle performance. Data at the onboard data by his periodically received by a microprocessor and passed into a local transmitter. The invention specifically calls out transmission of data on a predetermined time interval. Thus these inventions do not anticipate nor include processing and analysis steps which result in data being passed at time other than expiration of the predetermined time period.

Reynolds and Reynolds Holding Inc., further describes systems where motor vehicles are coupled by wireless communications links to remote host servers in U.S. Pat. No. 6,732,031.

While systems and inventions of the art are designed to achieve particular goals and objectives, some of those being no less than remarkable, these inventions have limitations which prevent their use in new ways now possible. Inventions of the art are not used and cannot be used to realize the advantages and objectives of the inventions taught herefollowing.

The inventions disclosure of U.S. patent application filed Dec. 9, 2005 having Ser. No. 11/299,028 is presented by this same inventor. Further, another U.S. application filed Dec. 8, 2005 having Ser. No. 11/297,669 is similarly presented by same inventor. In addition, another U.S. application filed Dec. 7, 2005, entitled: “Memory Management in Event Recording Systems” serial number unknown; this application will be amended to properly reflect the serial number as soon as it is known, is also presented by instant inventor. Each of these disclosures include material which is critically important to a full understanding of important concepts relating to vehicle event recording systems. Accordingly, these disclosures are hereby incorporated here by explicit reference.

SUMMARY OF THESE INVENTIONS

Comes now, James Plante with inventions of vehicle event recorders having integrated web servers.

Vehicle event recorders having integrated web server modules are first presented herein this disclosure. A vehicle event recorder is arranged as a video camera, microprocessor, memory among other supporting subsystems such that when a predetermined event occurs, in example a car crash or unexpected impact, a video record of the incident is preserved. In these inventions, such vehicle event recorders are further provided with an advanced interface system. A web server module is incorporated and arranged as part of the included computer system. Thus, the system and all its subsystems may be addressed via hypertext transfer protocol, http, type transactions and commands. Users can interact with vehicle event recorder units of these inventions with nothing other than any standard computer. It is no longer necessary to load, manage, and maintain, proprietary application specific software on a user's workstation computer. Rather, a user may manipulate system settings, view and transfer files, receive e-mail alerts, and otherwise completely control the device as its functionality is entirely exposed by the integrated web server and complementary computing systems.

As a consumer product, a vehicle event recorder may be installed in a family vehicle without special knowledge or skill. The device operates to collect video and other vehicle performance information while the vehicle is in normal operation. Upon connection to a computer network, or more specifically a home computer network, a simple computer workstation equipped with a web browser can address the vehicle event recorder as the web server is responsive to requests sent by the web browser.

In addition, these systems include pre-programmed ‘web pages’ or ‘web forms’. These pages may be implemented as computer files stored in a ROM or DRAM, et cetera, of the vehicle event recorder. They are pre-programmed with interconnects and preset relationships with subsystems. For example, these pages may be provide an interface to camera settings such as brightness and contrast, et cetera.

Further, in some versions, a file transfer protocol server and simple mail transfer protocol servers are also included. These servers also support general interface mechanisms which permit standard computers to interact with these vehicle event recorders without requiring installation of special software and hardware systems.

OBJECTIVES OF THESE INVENTIONS

It is a primary object of these inventions to provide vehicle event recorders and vehicle event recorder systems.

It is an object of these inventions to provide vehicle event recorders with an improved user interface.

It is a further object to eliminate previously required workstation desktop applications and complex external communications mechanisms and protocol.

It is an object of these inventions to provide interface to vehicle event recording systems via standard computing platforms and ubiquitous software.

A better understanding can be had with reference to detailed description of preferred embodiments and with reference to appended drawings. Embodiments presented are particular ways to realize these inventions and are not inclusive of all ways possible. Therefore, there may exist embodiments that do not deviate from the spirit and scope of this disclosure as set forth by appended claims, but do not appear here as specific examples. It will be appreciated that a great plurality of alternative versions are possible.

BRIEF DESCRIPTION OF THE DRAWING FIGURES

These and other features, aspects, and advantages of the present invention will become better understood with regard to the following description, appended claims and drawings where:

FIG. 1 is a simple block diagram showing relationships between primary elements of systems of these inventions;

FIG. 2 is a block diagram of a vehicle event recorder head;

FIG. 3 illustrates the relationship a vehicle event recorder video camera has with its exterior and further illustrates other important elements of the vehicle event recorder head;

FIG. 4 illustrates transactions over a network element of these vehicle event recorder systems;

FIG. 5 illustrates an example browser type user interface associated with these systems;

FIG. 6 illustrates a second page of a browser having various system control functions which may be manipulated via the browser;

FIG. 7 illustrates an important network architecture and connection associated with these systems;

FIG. 8 illustrates in diagram several additional important functions which may be incorporated within a vehicle event recorder head; and

FIG. 9 illustrates an important network configuration which permits remote access to vehicle event recorder heads.

GLOSSARY OF SPECIAL TERMS

Throughout this disclosure, reference is made to some terms which may or may not be exactly defined in popular dictionaries as they are defined here. To provide a more precise disclosure, the following terms are presented with a view to clarity so that the true breadth and scope may be more readily appreciated. Although every attempt is made to be precise and thorough, it is a necessary condition that not all meanings associated with each term can be completely set forth. Accordingly, each term is intended to also include its common meaning which may be derived from general usage within the pertinent arts or by dictionary meaning. Where the presented definition is in conflict with a dictionary or arts definition, one must use the context of use and liberal discretion to arrive at an intended meaning. One will be well advised to error on the side of attaching broader meanings to terms used in order to fully appreciate the depth of the teaching and to understand all the intended variations.

Web Browser

A web browser is a computer graphical user interface operable for receiving computer files and presenting a graphical display which may have interactive elements sometimes called ‘controls’ or web controls. Further, a browser is operable for sending requests in the form of a computer file—generally both received and sent files are in a format such as XML or more familiarly HTML.

Web Server

A web server is implemented as a special module of a computer and is operable for exchanging information via computer files—generally files in XML/HTML formats. A web server receives requests and returns responses to external parties via a communications link.

Web Request

A web request is a data transmission arranged in agreement with Internet protocol directed to a specific web server.

Web Response

A web response is a data transmission by a web server arranged in agreement with Internet protocol and directed toward a requesting agent usually a web browser.

Physical Anomaly

Any change in a prescribed physical parameter which is defined as outside the scope of normal operating conditions.

Managed Loop Memory

A ‘managed loop memory’ is a memory system arranged to preserve in detail data captured during a period immediately past with respect to any instant but to overwrite that data with newer data when that data has sufficiently aged in accordance with a predefined expiration definition.

Vehicle Environments

The environment in and about a vehicle includes those spaces interior or exterior with respect to the car body. That is to say, traffic ahead of, behind, towards the sides of, and inside the driver compartment are all included as vehicle environments.

Communications Port

Includes means for supporting a data communications link including a transceiver or modem arrangement and suitable connection apparatus. Some examples include: a mobile cellular transceiver; WiFi; WiMax; bluetooth; Ethernet; serial port such as RS-232; among others.

PREFERRED EMBODIMENTS OF THESE INVENTIONS

In accordance with each of preferred embodiments of these inventions, vehicle event recorders having integrated Web servers are provided. It will be appreciated that each of embodiments described include apparatus and that the apparatus of one preferred embodiment may be different than an apparatus of an alternative embodiment.

Vehicle event recorders first presented here are generally characterized as including: a video camera, microprocessor, memory, and web server module. Video images are captured during use of the vehicle. When a particular ‘event’ occurs, a captured video series is saved to a durable memory. When the vehicle is returned to a location where network connectivity is available, the captured video series is made available for review via a web server. The integrated web server, when connected to a TCP/IP network, can receive requests for information from external web browsers. These requests for information may be directed as requests to view data captured during a recent previous operation period. The web server is suitably coupled to a memory whereby data and files stored there may be transferred to the requesting web browser. Accordingly, web servers of these systems expose data captured by the device, including video data of scenes about the vehicle captured during vehicle use. In addition, these web servers are also coupled to system settings and operational parameters whereby adjustments to those settings and parameters may be effected via a web browser. For example, trigger threshold values may be set to be more or less sensitive. An event trigger system arranged to detect an abrupt acceleration action may include an adjustable sensitivity level. Via web browser interface, the event trigger threshold can be set by a remote user operating a standard web browser in communication with the device web server. A web server is part of a complement pair which forms a user interface system. A web server and web browser connected together via a TCP/IP network form an interface system which is convenient and very powerful. Complete control of the device is permitted because prerecorded “web pages” or “web forms” may be prepared as part of the web server. These pages and the controls thereon may be coupled to physical systems of the device. In this way, the user having no other tools than a standard computer with a web browser is able to completely interface with the system. As such, proprietary software and the complexity and inconvenience associated therewith are completely eliminated.

With reference to FIG. 1, the reader will gain further appreciation of architecture relating to apparatus of these inventions. In particular, vehicle event recorder head unit 1 with integrated web server 2 is installed in a motor vehicle such as a common family car 3. The vehicle event recorder head is coupled by way of a data communications link 4, preferably a TCP/IP network to a computer workstation 5 operable for running a web browser 6. The arrangement provides a graphical user interface to a remotely located user 7, and further, means of remote input and interaction with the vehicle event recorder by way of common computer keyboard 8 for example. A user, in the comfort of a computer workplace, can provide a vehicle event recorder mounted in an automobile with instruction, update, interaction, download, review, among others. Functionality exposed by the vehicle event recorder becomes available to users working at a workstation by way of a common computer or ‘Internet browser’ graphical user interface. For example, a user can use simple browser control interfaces to set the camera contrast and brightness while at a workstation not in, or even not near, the car.

A vehicle event recorder with integrated web server is installed in the vehicle whereby a video camera has a clear view of the space and surroundings in front of the car. In this way, should the unfortunate occasion of a traffic accident occur, the video camera can provide a video record of traffic conditions and events leading up to the accident. A video series, including images captured just prior and just after an event moment as initiated by an event trigger, the series relating to an accident, is saved in a vehicle event recorder local memory. At a later time, when the vehicle is appropriately coupled to a workstation by suitable communications link, video series data can be transferred to the workstation where it may be further viewed and analyzed. A vehicle may be coupled to a workstation by communications link of several alternative forms including at least an Ethernet hardware connection, a WiFi wireless communications link, a Bluetooth communications link, a wireless mobile telephone network link, among others. Workstations used in these arrangements are of the type common to nearly every desktop in every home or office. While a workstation alone is insufficient for interacting with vehicle event recorders of these inventions, a workstation with a ‘web browser’ or ‘Internet browser’ such as the Windows™ Internet Explorer is an ideal combination for providing access to vehicle event recorders so arranged. Of course, competing web browsers such as FireFox, Opera, Konqueror, Safari, Gecko, et cetera may be used with nearly identical effect. In all cases, these browsers will communicate with a vehicle event recorder because they all can read, parse and produce appropriate XML and HTML transactions. Thus, it is not necessary for users of these systems to buy, subscribe to, install, learn to use, maintain, update, re-install, among others, any proprietary software. Rather, these vehicle event recorders expose their functionality to any computer running a web browser of a user's choice.

In all prior art versions of similar systems, workstations are coupled to vehicle event recorders by way of proprietary application-specific software running on the workstation. Thus, it is impossible in those systems to manipulate and control a vehicle event recorder with a general purpose computer not having specially prepared programming. Data exchanges between a workstation application of the prior art and those vehicle event recorders typically include proprietary calls and file and object formats not compatible with general-purpose applications. In contrast, as the unique vehicle event recorders first presented here include a built-in web server, users have access to inner workings and settings of the vehicle event recorder by way of ‘http’ transactions. Further, simple data transfer including large video files may be taken up and handled by the same web server or by an accompanying ftp (file transfer protocol) server.

In some preferred versions, data communications link 4 is a common home network. A vehicle parked in the household garage becomes coupled to the home network by way of its proximity to a WiFi router for example. When a teenage driver returns home, mom instantly has access to information including video of her children's driving activity by way of her internet browser.

A top-level block diagram of a video event recorder is presented as FIG. 2. Video event recorders 21 of these inventions are comprised of the primary elements including: a video camera 22, a microprocessor 23, a web server 24, memory 25, and a communications port 26. A typical arrangement of a vehicle event recorder includes having these elements combined within a small plastic housing suitable for being mounted near or at a car windshield. It is preferable to install these devices on the interior portions of a vehicle in the passenger/occupant space. While the elements described together in combination form a vehicle event recorder head, sometimes reference herein is made to a ‘vehicle event recorder system’. When a head unit is coupled with a network or communications path which includes a workstation or other server remote from the vehicle event recorder head, the ensemble is considered a ‘vehicle event recorder system’.

FIG. 3 presents further detail with regard to the architecture of these vehicle event recorders 31. The camera field-of-view 32 may be arranged in ‘forward looking’ direction such that images of activity ahead of the vehicle are captured by the camera. Thus, it is said that the camera is coupled to environments about the vehicle. The video camera is further coupled electronically 33 to the microprocessor whereby the camera may transmit image data thereto. The microprocessor is further coupled electronically 34 to a memory which may be managed by the microprocessor to store image series associated with particular events such as traffic accidents. For example, upon receipt of signal from an event trigger 35, a short video series stored in managed loop memory 36, may be transferred to a more permanent stable memory, such as a high-capacity flash type memory 37. Finally, the web server 38 is coupled to a communications port 39 which permits the web server to interact with exterior computing systems.

In some preferred versions, cameras are arranged as forward looking cameras, others are rearward looking cameras, and still others as driver compartment view cameras. The number of cameras associated with a single vehicle recorder unit is meant to be not limited to one.

In preferred versions, a local memory is arranged to capture and preserve video information associated with a time prior to, and after, an important event. A managed loop memory includes an overwrite process which preserves data for a limited time and overwrites data as soon as it has aged in accordance with an overwrite scheme. Upon the occurrence of a ‘triggered event’—a car crash for example—the loop memory data is transferred to a buffer where it may be saved without subject to overwrite for an extended time.

An event trigger is arranged to detect a physical anomaly such as a high acceleration associated with a crash or other impact; alternatively a heavy swear or excessive braking maneuver; or even as a response to a panic button strike. The event trigger declares the occurrence of an incident and sets the memory to preserve all data associated with the incident or event.

A web server of these systems preferably includes preformed ‘web pages’ or sometimes ‘web forms’. In some advanced versions, these can be arranged in accordance with the Microsoft technology ASP.NET or sometimes referred to as Active Server Pages. These pages offer great latitude in providing web controls which are coupled to the internal systems of the vehicle event recorder systems. For example, the video camera may be controlled in that its contrast, brightness and intensity can be manipulated via such web controls on ASP.NET pages.

Because a car is easily coupled to a home computer network via a WiFi system, preferred versions include vehicle event recorder units having an output port fashioned as a WiFi or WiMax transceiver. Alternatives may include other radio type transceivers such as bluetooth, or optical type wireless links such as those which exploit infrared optical coupling. Of course, while not as convenient, it is entirely possible that a parked car be coupled to a home network via a hardwired Ethernet connection. A vehicle event recorder arranged with a common network interface card could be plugged in with hardwire (RJ45 type connector) to a local Ethernet system.

A web server is sometimes considered a part of the microprocessor or other computing platform, as it may be embodied as a computer code module running thereon. In FIG. 3, it is drawn separately from the microprocessor to bring emphasis to its importance. While known vehicle event recorders have been arranged with common microprocessors, it is first suggested here that a web server module be included and provide interface between a vehicle event recorder microprocessor and an external computing system. In this way, access to the microprocessor and vehicle event recorder subsystem functionality is provided to any computer system which address the web server with appropriate http transactions. That is, the web server is arranged to receive well-formed http requests (in example, http ‘GET’ commands), and further to provide responses constructed as http answers (http ‘POST’ responses).

FIG. 4 illustrates more clearly a particular example of a transaction between a user operating at a computer workstation 41, with installed Web browser 42, linked by a communications link to a vehicle event recorder 43 having integrated web server 44 installed in a common family automobile 45. From the workstation keyboard, the user 46 may inquire as to the state of the vehicle event recorder by sending an http request in the form of a GET type command 47. A GET command is fashioned as an http request and includes the URL of the source being addressed—the ‘web address’ of the vehicle event recorder; and perhaps an introduction web form or home/default web form. For example, a particular web page providing access to certain desired functionality may have a URL as follows: “http://192.168.1.8/camerasettings.aspx”. A GET command 47 including that URL is formed by and transmitted from the workstation's web browser to the vehicle event recorder's web server (having IP address 192.168.1.8). Upon receipt of the GET command, the web server responds by providing a POST action 48—an http response. The POST action may include transmission of an XML or/and HTML coded web page, which may be appropriately interpreted and displayed by the web browser and its graphical user interface or sometimes ‘window’ presented to the user on a system monitor 49.

To better explain what is meant by the phrase: ‘the state of the vehicle event recorder’ presented above, one might consider the following text in conjunction with the drawing presented as FIG. 5. FIG. 5 illustrates an example of a web page served by the web server of a vehicle event recorder. A web page is sometimes comprised a interactive objects sometimes and herein referred to as “web controls”. These include such controls commonly known as: ‘menus’; ‘toolbars’; ‘drop-down boxes’; ‘listboxes’; ‘radio buttons’; ‘checkboxes’; ‘sliders’; ‘textboxes’, among others. In FIG. 5, browser window 51 includes a field having a page title 52: “SmartDrive™ Camera Setup”. Further, the browser window includes a graphical element known as a menu or menu bar 53, and toolbar 54. Icons associated with various functionality are laid across a horizontal strip. When a user ‘clicks’ any of these icons, it sets into motion a computer code module to effect some operation. A very important aspect of any web browser include the address line 55. An address line may contain the URL or web address of the source currently displayed. This address may be typed-in manually by a user, or it may have been arrived at by way of a hyperlink from another page displayed previously in the browser window. Typical web browser windows further include other interactive objects such as a search engine interface including a drop-down box 56, a command button controls 57, slider controls 58, textboxes 59, an ‘option’ or radio buttons 510. From these web controls, a user interface is brought about and designed for interaction with the available functions in a vehicle event recorder hosting the associated web pages on its web server. A user may adjust a control and thereafter send the state of the web page to the vehicle event recorder unit. This is accomplished by ‘pointing’ and ‘clicking’ to change the control settings and then submitting the page or posting the page to the web server in the vehicle event recorder. In example, one may adjust the contrast of the camera by using slider control 58 and thereafter submit button 511 which results in the page being posted back to the web server and ultimately the contrast being improved. A careful observer will note that each of command button controls 57 may lead to a different association of certain functions in groups. The functions of the camera are grouped into those which are displayed in that field 512. If the command button associated with system functions is chosen, then the available functions in field may change without appreciable change to the general form of the page. FIG. 6 illustrates.

A group of controls associated with system function is presented in the diagram of FIG. 6 which is a graphical user interface embodied as a web page 61. Command button control 62 associated with the system settings is called at the browser by way of this page's URL http://192.168.1.8/systemsettings.htm 63. The page permits a user to adjust the IP address 64 of the vehicle event recorder at textbox 65. A user may choose a particular enhanced timeline at a drop down box 66 as prescribed by those available in a managed loop memory system. User data/profile can be entered at textbox 67 and command button 68 can be used to save a username to a memory in the vehicle event recorder. Finally, a trigger threshold can be set on a continuous slider control 69 to make an event trigger in the vehicle event recorder either more or less sensitive. In this way, a user at a remote computer running a simple internet browser makes adjustments directly to a vehicle event recorder installed in a vehicle.

While sometimes these web servers are arranged with pre-programmed ‘web page’ objects addressable via web request actions, they may also include programmed modules known as web services. These functions, properties and events, do not have a user interface associated with them, however they include transaction interface which permits their being addressed via TCP/IP web requests. These functions, properties and events may be coupled to subsystems of the vehicle event recorder head. For example, an ‘authorized users list’ may be adjusted whereby log-on actions by users are enabled/disabled. This web service may be taken up automatically in response to some condition being met. Therefore, without user interaction via a web page, but rather by purely automated processes, i.e. web services, these vehicle event recorder systems may be adjusted and otherwise manipulated.

Best modes of these inventions are illustrated in FIG. 7. A vehicle 71 is prepared with a vehicle event recorder unit 72 having therewith an integrated web server 73. A communications port, in example a WiFi transceiver 74 permits the vehicle event recorder to connect wirelessly to a home network by way of complimentary WiFi transceiver/router 75. When the car enters a zone or space 76 served by the transceiver/router, the vehicle event recorder web server is accessible by a user 77 operating workstation 78 running a web browser 79 program. The user may adjust, upload, download, browse, and otherwise interact with the vehicle event record and data stored on the vehicle event recorder.

In special advanced versions, vehicle event recorders additionally include modules other than a simple web server. For example, an vehicle event recorder may additionally include a file exchange and e-mail server systems. FIG. 8 shows graphically a vehicle event recorder 81 for use in conjunction with vehicle 82, the vehicle event recorder comprising an integrated web server 83, a file transport protocol ftp server 84, and an e-mail (SMTP) server 85. The web browser 86 at a user workstation 87 similarly communicates with these elements in a conventional way to bring about these functions in a vehicle event recorder. In this way, automatic triggers can be arranged in the vehicle event recorder such that it can send e-mail messages in response to certain events having been ‘fired’ in the normal processing of the system. When something of interest occurs, an e-mail message is prepared and queued. On the next occasion where the vehicle event recorder is connected to the internet, the SMTP sends the e-mail to the intended recipient. In a similar fashion, the vehicle event recorder ftp server operates to send and receive data files.

While most preferred versions are arranged with the primary objective being a home, family or small number user local systems, these inventions are also meant to include as a special case the need for remote operation. A private home computer network can be arranged with a public port which exposes certain services through a firewall to the public internet. In this way, a vacationing parent can still have a look at the vehicle use records from afar. Vehicle 91 equipped with vehicle event recorder 92 having integrated web server communicates with local radio 93 as it enters communications space 94. the mere act of the vehicle entering 95 the space causes the vehicle event recorder to become connected to the network which may include the Internet. Accordingly, a communications link 96 of many thousands of miles is possible whereby a user 97 working on any workstation 98 equipped with a browser can address the web, file and mail servers of the remotely located vehicle event recorder.

One will now fully appreciate how a vehicle event recorder having an integrated web server is used to provide simple user access to operation and function of these systems. Although the present inventions have been described in considerable detail with clear and concise language and with reference to certain preferred versions thereof including best modes anticipated by the inventors, other versions are possible. Therefore, the spirit and scope of the invention should not be limited by the description of the preferred versions contained therein, but rather by the claims appended hereto. 

1) Vehicle event recorders comprising: a video camera; a microprocessor; a memory; a web server module; and a communications transceiver, the video camera having a field-of-view coupled to environments about a vehicle and an electronic output coupled to the microprocessor, the microprocessor coupled to the memory whereby image data from the video camera may be stored in the memory, and the web server module electronically coupled to the communications transceiver arranged to receive and process data transactions in accordance with Internet protocols. 2) Vehicle event recorders of claim 1, said web server module further comprises prearranged web pages comprising web controls, whereby said web pages and web controls are operable for being presented as graphical user interfaces in a standard web browser. 3) Vehicle event recorders of claim 2, said web controls are coupled to subsystems whereby adjustments made at the web control graphical user interface are transmitted to physical subsystems of the vehicle event recorder to effect adjustment therein those subsystems. 4) Vehicle event recorders of claim 3, said subsystems are any of those from the group comprising: camera brightness, camera contrast, camera intensity, camera resolution, camera frame rate, camera image color, event trigger threshold, managed loop memory timeline scheme, and communications transceiver IP address. 5) Vehicle event recorders of claim 2, said web pages are further characterized as ASP.NET type active server pages. 6) Vehicle event recorders of claim 1, said memory is fashioned as a managed loop memory having an overwrite scheme expired frames are replaced by newer frames. 7) Vehicle event recorders of claim 6, further comprises an event trigger arranged to detect a physical anomaly and cause a data transfer from said managed loop memory to a buffer memory. 8) Vehicle event recorders of claim 1, said web server module further comprises prearranged web services comprising programming modules which may be invoked via TCP/IP calls to them from a web browser. 9) Vehicle event recorders of claim 8, said web services are further characterized as system functions, properties and events associated with the vehicle event recorder head which control its parameters and actions. 10) Vehicle event recorders of claim 9, said web services include computer functionality having an interface adopted to TCP/IP transactions. 11) Vehicle event recorders of claim 1, further comprising a file transfer protocol server. 12) Vehicle event recorders of claim 1, further comprising a simple mail transfer protocol server. 13) Vehicle event recorders of claim 1, said communications transceiver is further characterized as a WiFi or WiMax compliant transceiver. 14) Vehicle event recorders of claim 1, said communications transceiver is further characterized as a cellular wireless transceiver. 15) Vehicle event recorders of claim 1, further comprising: a data transmission network, a workstation, and a web browser, said data transmission network support packet traffic via TCP/IP, and said web browser is embodied as software running on said workstation. 16) Vehicle event recorders of claim 15, said data transmission network includes a portion characterized as a local area network LAN or home type network. 17) Vehicle event recorders of claim 16, said data transmission network further comprises at least one router operable for directing data traffic in accordance with Internet protocol. 18) Vehicle event recorders of claim 16, said data transmission network is a compound network comprising a wired portion and a wireless portion. 19) Vehicle event recorders of claim 18, said router is a WiFi or WiMax router and the vehicle event recorder communications transceiver is a complementary WiFi or WiMax transceiver. 20) Vehicle event recorders of claim 18, said data transmission network further comprises a protocol gateway interface between a TCP/IP network and a mobile cellular communications network. 